It was reported that after updating version numbers for aliases in a .CSV file, the applicable accounts pointed to the wrong content set.
This issue has been resolved; code changes were made to resolve data discrepancies that existed in the database.
No user action is required.